\f0\fs28 is being uncooperative. Specifically, if someone polls my machine, my machine hangs up the phone (the other side typically sees this after the second\
\
\f1\fs24\li700 imsg looking for SYNC<\
\f0\fs28\li0 \
message in the debug output). When I poll that same machine,
\f1\fs24 uucico
\f0\fs28 gives me a core dump, after a segmentation fault. What's stranger still is that polling
\i some
\i0 machines works fine, and those machines can poll mine!\
\
Q:
\f1\fs24 uucico
\f0\fs28 is crashing when it tries to transfer files other than mail. Mail comes through fine, but a file transfer won't. What's wrong?\
\
A: What's likely the problem is that you have improperly formatted UUCP configuration files. For example, blank lines in your
\f1\fs24 L.sys
\f0\fs28 file can cause the first symptom, and malformed lines in your
\f1\fs24 USERFILE
\f0\fs28 can cause the second.. The UUCP system can't handle these.\
\
In the case of the blank
\f1\fs24 L.sys
\f0\fs28 line, if the line is entirely empty -- no spaces, no tabs, just empty -- uucico will work fine. However, if the line contains only whitespace -- spaces and tabs -- then uucico will crash. Remove the blank lines, or, if you like white space in your
\f1\fs24 L.sys
\f0\fs28 file, replace the blank lines with otherwise-empty comment lines.\
\
In addition, if expected fields are missing, uucico has been known to crash. For example, the following
\f1\fs24 L.sys
\f0\fs28 entry will crash uucico:\
\
\f1\fs24\li700\fc0 … \\\
"" ATdt555-1212 \\\
ogin:~20- -ogin:- -ogin: name \\\
ssword: YouKnowWhat\
\f0\fs28\li0 \
What was
\i desired
\i0 in this case was to send a newline if the prompt
\b ogin:
\b0 was not received. What happened instead is that uucico was looking for the next
\i expect
\i0 string in the
\i expect-send
\i0 sequence, and it wasn't there. To accomplish this, use the following instead:\
\
\f1\fs24\li700 … \\\
"" ATdt555-1212 \\\
ogin:~20-CR-ogin:-CR-ogin: name \\\
ssword: YouKnowWhat\
\f0\fs28\li0 \
In the case of a malformed USERFILE, check for lines with a missing space. The format of USERFILE is\
\
\f1\fs24\li700 [user],[system] directory\
\f0\fs28\li0 \
You
\i must
\i0 have the space between the
\f1\fs24 user,system
\f0\fs28 and the directory. (Yes,
\f1\fs24 user
\f0\fs28 and
\f1\fs24 system
\f0\fs28 are both optional. The comma between them and the space following them are not.)\
\
One other thing which can cause uucico to fail (silently on the remote, with a bus error locally) is if the program — which runs SetUID uucp and SetGID daemon — does not have appropriate access to the UUCP spool directory,
\f1\fs24 /usr/spool/uucp
\f0\fs28 . Ensure that the user
\b uucp
\b0 can read, write, and search (“execute”) the spool directory. Recommended permissions are 755 (read, write, execute for the user; read, execute for the group; read, execute for others).\